Storage traffic pattern detection in memory devices

ABSTRACT

A processing device of a memory sub-system can monitor a plurality of received commands to identify a forced unit access command. The processing device can identify a metadata area of the memory device based on the forced unit access command. The processing device can also perform an action responsive to identifying a subsequent forced unit access command to the metadata area.

TECHNICAL FIELD

Embodiments of the disclosure relate generally to memory sub-systems,and more specifically, relate to storage traffic pattern detection inmemory devices.

BACKGROUND

A memory sub-system can include one or more memory devices that storedata. The memory devices can be, for example, non-volatile memorydevices and volatile memory devices. In general, a host system canutilize a memory sub-system to store data at the memory devices and toretrieve data from the memory devices.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure will be understood more fully from the detaileddescription given below and from the accompanying drawings of variousembodiments of the disclosure.

FIG. 1 illustrates an example computing system that includes a memorysub-system in accordance with some embodiments of the presentdisclosure.

FIG. 2 is a graph illustrating LBAs to which a sequence of commands aredirected in accordance with some embodiments of the present disclosure.

FIG. 3 illustrates an example of a method for identifying a journal areain accordance with some embodiments of the present disclosure.

FIG. 4 is a graph illustrating LBAs to which a sequence of commands aredirected and a number of tables corresponding thereto in accordance withsome embodiments of the present disclosure.

FIG. 5 illustrates an example of a metadata area in accordance with someembodiments of the present disclosure.

FIG. 6 illustrates an example of a metadata area in accordance with someembodiments of the present disclosure.

FIG. 7 is a flow diagram of an example method for detection circuitry inaccordance with some embodiments of the present disclosure.

FIG. 8 is a block diagram of an example computer system in whichembodiments of the present disclosure may operate.

DETAILED DESCRIPTION

Various embodiments of the present disclosure are directed to memorysub-systems for storage traffic pattern detection in memory devices. Amemory sub-system can be a storage device, a memory module, or a hybridof a storage device and memory module. Examples of storage devices andmemory modules are described below in conjunction with FIG. 1. Ingeneral, a host system can utilize a memory sub-system that includes oneor more memory devices, such as memory devices that store data. The hostsystem can provide data to be stored at the memory sub-system and canrequest data to be retrieved from the memory sub-system.

The host system can send access requests (e.g., write command, readcommand) to the memory sub-system, such as to store data on a memorydevice of the memory sub-system and to read data from the memory device.The data to be read or written, as specified by a host request, ishereinafter referred to as “host data” or “user data”. A host requestcan include logical address information (e.g., logical block address(LBA), namespace) for the host data, which is the location the hostsystem associates with the host data. The host system can implement afile system to store the host data/user data in the memory sub-system.As used herein, a file system can comprise software that is implementedto control how data is stored and/or retrieved from the memorysub-system.

Write sequences for a particular file system can include write commandsfor a portion of memory that stores metadata. Write commands to logicalblock addresses (LBAs) may be stored in cache. Periodically, the datastored to the cache can be committed to a memory device of the memorysub-system. Some systems (e.g., EXT4 file system) block operations tothe storage device until data and related metadata movement from cacheto a memory device is successfully completed. The inability to processcommands at a memory sub-system can lead to perceived system lag by auser. For example, some accesses to a file system may be temporarilyunavailable (e.g., blocked) until particular operations, which may beconsidered system critical, are successfully completed. Such operationscan include writes to particular metadata areas, which may be inassociation with a journal commit operation or other operation designedto maintain data integrity, for example. Accordingly, the unavailabilityof the file system for processing user level commands while it servicesparticular metadata writes can be perceived as system lag, which maydegrade user experience.

Various embodiments of the present disclosure address the above andother deficiencies. For example, a number of embodiments can provide forimproved latency of operations directed to metadata areas associatedwith a file system, thereby improving user experience. For example, anumber of embodiments can include identifying a particular file systembased on input/output (IO) patterns. A particular area (e.g., LBA range)of the memory device used to store metadata for the file system can alsobe identified, and actions can be taken in order to improve the latencyof accesses to the identified metadata areas. For example, such metadataarea accesses may be prioritized over various other operations such asbackground and/or housekeeping operations including garbage collectionoperations.

As used herein, metadata refers to data that describes different data.Metadata can include data that describes file structures and/or datathat describes a file system. For instance, metadata can be used fordata integrity. Metadata can include specialized data structures whichcan describe internal file system structures (e.g., EXT4 journal). Ametadata area describes a portion (e.g., LBA range) of memory deviceused to store the metadata.

The figures herein follow a numbering convention in which the firstdigit or digits correspond to the drawing figure number and theremaining digits identify an element or component in the drawing.Similar elements or components between different figures may beidentified by the use of similar digits. For example, 221 may referenceelement “21” in FIG. 2, and a similar element may be referenced as 421in FIG. 4. Analogous elements within a figure may be referenced with ahyphen and extra numeral or letter. See, for example, elements 226-1, .. . , 226-5 in FIG. 2. As will be appreciated, elements shown in thevarious embodiments herein can be added, exchanged, and/or eliminated soas to provide a number of additional embodiments of the presentdisclosure. In addition, as will be appreciated, the proportion and therelative scale of the elements provided in the figures are intended toillustrate certain embodiments of the present invention and should notbe taken in a limiting sense.

FIG. 1 illustrates an example computing system 100 that includes amemory sub-system 103 in accordance with some embodiments of the presentdisclosure. The memory sub-system 103 can include media, such as one ormore volatile memory devices (e.g., memory device 106), one or morenon-volatile memory devices (e.g., memory device 105), or a combinationof such.

A memory sub-system 103 can be a storage device, a memory module, or ahybrid of a storage device and memory module. Examples of a storagedevice include a solid-state drive (SSD), a flash drive, a universalserial bus (USB) flash drive, an embedded Multi-Media Controller (eMMC)drive, a Universal Flash Storage (UFS) drive, a secure digital (SD)card, and a hard disk drive (HDD). Examples of memory modules include adual in-line memory module (DIMM), a small outline DIMM (SO-DIMM), andvarious types of non-volatile dual in-line memory module (NVDIMM).

The computing system 100 can be a computing device such as a desktopcomputer, laptop computer, network server, mobile device, a vehicle(e.g., airplane, drone, train, automobile, or other conveyance),Internet of Things (IoT) enabled device, embedded computer (e.g., oneincluded in a vehicle, industrial equipment, or a networked commercialdevice), or such computing device that includes memory and a processingdevice.

The computing system 100 can include a host system 102 that is coupledto one or more memory sub-systems 103. In some embodiments, the hostsystem 102 is coupled to different types of memory sub-systems 103. FIG.1 illustrates an example of a host system 102 coupled to one memorysub-system 103. As used herein, “coupled to” or “coupled with” generallyrefers to a connection between components, which can be an indirectcommunicative connection or direct communicative connection (e.g.,without intervening components), whether wired or wireless, includingconnections such as electrical, optical, magnetic, and the like.

The host system 102 can include a processor chipset and a software stackexecuted by the processor chipset. The processor chipset can include oneor more cores, one or more caches, a memory controller (e.g., NVDIMMcontroller), and a storage protocol controller (e.g., peripheralcomponent interconnect express (PCIe) controller, SATA controller). Thehost system 102 uses the memory sub-system 103, for example, to writedata to the memory sub-system 103 and read data from the memorysub-system 103.

The host system 102 can be coupled to the memory sub-system 103 via aphysical host interface. Examples of a physical host interface include,but are not limited to, a serial advanced technology attachment (SATA)interface, a PCIe interface, universal serial bus (USB) interface, FibreChannel, Serial Attached SCSI (SAS), Small Computer System Interface(SCSI), a double data rate (DDR) memory bus, a dual in-line memorymodule (DIMM) interface (e.g., DIMM socket interface that supportsDouble Data Rate (DDR)), Open NAND Flash Interface (ONFI), Double DataRate (DDR), Low Power Double Data Rate (LPDDR), or any other interface.The physical host interface can be used to transmit data between thehost system 102 and the memory sub-system 103. The host system 102 canfurther utilize an NVM Express (NVMe) interface to access the memorycomponent (e.g., memory devices 105) when the memory sub-system 103 iscoupled with the host system 102 by the PCIe interface. The physicalhost interface can provide an interface for passing control, address,data, and other signals between the memory sub-system 103 and the hostsystem 102. FIG. 1 illustrates a memory sub-system 103 as an example. Ingeneral, the host system 102 can access multiple memory sub-systems viaa same communication connection, multiple separate communicationconnections, and/or a combination of communication connections.

The memory devices 105, 106 can include any combination of the differenttypes of non-volatile memory devices 105 and/or volatile memory devices106. The volatile memory devices (e.g., memory device 106) can be, butare not limited to, random access memory (RAM), such as dynamic randomaccess memory (DRAM) and synchronous dynamic random access memory(SDRAM).

Some examples of non-volatile memory devices (e.g., memory device 105)include negative-and (NAND) type flash memory and write-in-place memory,such as three-dimensional cross-point (“3D cross-point”) memory device,which is a cross-point array of non-volatile memory cells. A cross-pointarray of non-volatile memory can perform bit storage based on a changeof bulk resistance, in conjunction with a stackable cross-gridded dataaccess array. Additionally, in contrast to many flash-based memories,cross-point non-volatile memory can perform a write in-place operation,where a non-volatile memory cell can be programmed without thenon-volatile memory cell being previously erased. NAND type flash memoryincludes, for example, two-dimensional NAND (2D NAND) andthree-dimensional NAND (3D NAND).

Each of the memory devices 105 can include one or more arrays of memorycells. One type of memory cell, for example, single level cells (SLC)can store one bit per cell. Other types of memory cells, such asmulti-level cells (MLCs), triple level cells (TLCs), quad-level cells(QLCs), and penta-level cells (PLCs) can store multiple bits per cell.In some embodiments, each of the memory devices 105, 106 can include oneor more arrays of memory cells such as SLCs, MLCs, TLCs, QLCs, or anycombination of such. In some embodiments, a particular memory device caninclude an SLC portion, and an MLC portion, a TLC portion, a QLCportion, or a PLC portion of memory cells. The memory cells of thememory devices 105, 106 can be grouped as pages that can refer to alogical unit of the memory device used to store data. With some types ofmemory (e.g., NAND), pages can be grouped to form blocks.

Although non-volatile memory devices 105 such as a 3D cross-point arrayof non-volatile memory cells and NAND type memory (e.g., 2D NAND, 3DNAND) and 3D cross-point array of non-volatile memory cells aredescribed, the memory device 105 can be based on any other type ofnon-volatile memory or storage device, phase change memory (PCM),self-selecting memory, other chalcogenide based memories, ferroelectrictransistor random-access memory (FeTRAM), ferroelectric random accessmemory (FeRAM), magneto random access memory (MRAM), Spin TransferTorque (STT)-MRAM, conductive bridging RAM (CBRAM), resistive randomaccess memory (RRAM), oxide based RRAM (OxRAM), negative-or (NOR) flashmemory, and electrically erasable programmable read-only memory(EEPROM).

The memory sub-system controller 104 (or controller 104 for simplicity)can communicate with the memory devices 105 to perform operations suchas reading data, writing data, or erasing data at the memory devices 105and other such operations. The memory sub-system controller 104 caninclude hardware such as one or more integrated circuits and/or discretecomponents, a buffer memory, or a combination thereof. The hardware caninclude a digital circuitry with dedicated (i.e., hard-coded) logic toperform the operations described herein. The memory sub-systemcontroller 104 can be a microcontroller, special purpose logic circuitry(e.g., a field programmable gate array (FPGA), an application specificintegrated circuit (ASIC), etc.), or other suitable processors.

The memory sub-system controller 104 can include a processor 107 (e.g.,a processing device) configured to execute instructions stored in alocal memory (e.g., not shown). The local memory of the memorysub-system controller 104 can include an embedded memory configured tostore instructions for performing various processes, operations, logicflows, and routines that control operation of the memory sub-system 103,including handling communications between the memory sub-system 103 andthe host system 102.

In some embodiments, the local memory can include memory registersstoring memory pointers, fetched data, etc. The local memory can alsoinclude read-only memory (ROM) for storing micro-code, for example.While the example memory sub-system 103 in FIG. 1 has been illustratedas including the memory sub-system controller 104, in another embodimentof the present disclosure, a memory sub-system 103 does not include amemory sub-system controller 104, and can instead rely upon externalcontrol (e.g., provided by an external host, or by a processor orcontroller separate from the memory sub-system).

In general, the memory sub-system controller 104 can receive commands oroperations from the host system 102 and can convert the commands oroperations into instructions or appropriate commands to achieve thedesired access to the memory devices 105 and/or the memory device 106.The memory sub-system controller 104 can be responsible for otheroperations such as wear leveling operations, garbage collectionoperations, error detection and error-correcting code (ECC) operations,encryption operations, caching operations, and address translationsbetween a logical address (e.g., logical block address (LBA), namespace)and a physical address (e.g., physical block address) that areassociated with the memory devices 105. The memory sub-system controller104 can further include host interface circuitry to communicate with thehost system 102 via the physical host interface. The host interfacecircuitry can convert the commands received from the host system intocommand instructions to access the memory devices 105 and/or the memorydevice 106 as well as convert responses associated with the memorydevices 105 and/or the memory device 106 into information for the hostsystem 102.

The memory sub-system 103 can also include additional circuitry orcomponents that are not illustrated. In some embodiments, the memorysub-system 103 can include a cache or buffer (e.g., DRAM) and addresscircuitry (e.g., a row decoder and a column decoder) that can receive anaddress from the memory sub-system controller 104 and decode the addressto access the memory devices 105. In various examples, a local memorycan comprise cache 111 that can be utilized in conjunction with thememory device 105/106.

In some embodiments, the memory devices 105 include a local mediacontroller 110 that operates in conjunction with memory sub-systemcontroller 104 to execute operations on one or more memory cells of thememory devices 105. An external controller (e.g., memory sub-systemcontroller 104) can externally manage the memory device 105 (e.g.,perform media management operations on the memory device 105).

In various examples, the memory sub-system 103 can be a managed NAND(MNAND) device in which an external controller (e.g., 104) is packagedtogether with one or more NAND die (e.g., 105). In an MNAND device, theexternal controller 104 can handle high level memory managementfunctions such as media management, and the local media controller 110can manage some of the lower level memory processes such as when toperform program-verify operations, MLC, TLC, QLC program operationsand/or calibrations, etc.

The memory sub-system controller 104 can also include a flashtranslation layer (FTL) 108. The FTL 108 can be responsible for variousfunction. For example, the FTL 108 can perform address translation(e.g., logical to physical), garbage collection, ECC, and wear leveling,among other functions performed by the FTL 108.

The memory sub-system controller 104 can also include a detectioncomponent 109. The detection component 109 can comprise an ASICconfigured to perform the examples described herein. While the detectioncomponent 109 can be implemented as circuitry (e.g., ASIC), thedetection component 109 can also be implemented as firmware and/orsoftware. For example, the firmware and/or software can includeinstructions, which when executed by the memory sub-system controller104, can cause the memory sub-system controller 104 to perform theexamples described herein such as the examples describe by FIGS. 3, 7,but not excluding the examples described in FIGS. 2, 4, 5, 6, 8.Although the detection component 109 is shown as being implementedseparate from the FTL 108, the detection component 109 can be part ofthe FTL 108. The detection component 109 can detect a metadata area ofthe memory devices 105/106. Types of metadata areas can vary dependingon the particular file system but can include a journal area, forexample. The detection component 109 can also determine a particularfile system 101 associated with writes to the metadata area(s) of thememory devices 105/106.

As used herein, the file system 101 controls how data is stored andretrieved. The file system 101 can control how data is separated asstored in the memory sub-system 103. The file system 102 can control thenaming of data and/or portions (e.g., separated portions) of data. Thefile system 102 can control the structure and logical rules used tomanage the data stored in the memory sub-system 103. The file system 101can be a network file system, a database file system, a transactionalfile system, and/or a mobile device file system, for example. A mobilefile system can be a fourth extended (EXT4) file system or a flashfriendly file system (F2FS), for example.

The detection component 109 can further detect an IO pattern for themetadata area and/or the user area of the memory devices 105/106. Asused herein, the terms detect, identify, and determine are usedinterchangeably.

The detection component 109 can, for instance, determine a file systemtype and/or a location of a metadata area (e.g., LBA range) associatedwith the file system based on a detected IO pattern. For example, forcedunit access commands of an IO pattern can be monitored (e.g., tracked)and used to identify a metadata area given that the file system metadataareas are often accessed via forced unit accesses. For instance, filesystems often employ forced unit access commands in a particularidentifiable pattern in association with accessing a metadata area.Therefore, the forced unit access commands can also be used to detect aparticular IO pattern. As used herein, a forced unit access command is awrite command whose corresponding data is written directly to the memorydevice, bypassing the write cache (e.g., the cache 111).

FIG. 2 is a graph illustrating LBAs to which a sequence of commands aredirected in accordance with some embodiments of the present disclosure.In FIG. 2, the x-axis represents time and the y-axis represents the LBAspace corresponding to the memory device. As shown in FIG. 2, the LBAspace includes a journal area 220. The remainder of the LBA space can beused for user data (e.g., the user LBAs), additional journal areas,and/or other metadata, for example.

The journal area 220 can be a dedicated metadata area of a journalingfile system used to track file system changes not yet committed tostorage. For example, the journal area 220 can store pointers to userLBAs and/or pointers to the journal area 220. The journal area 220 canalso be referred to as a journal 220. The journal 220 can be implementedas a circular buffer. As an example, the journal 220 described inassociation with FIG. 2 can be associated with a journal block device ofa journaling file system such as the extended 4 (EXT4) file system forLinux. Although the examples described in association with FIGS. 2-4relate to an EXT4 file system, embodiments are not limited to aparticular type of journaling file system.

FIG. 2 illustrates a plurality of write commands 223, journal writecommands 224-1, 224-2, 224-3, and 224-4 (referred to collectively asjournal write commands 224), and journal commit commands 225-1, 225-2,225-3, and 225-4 (referred to collectively as journal commit 225). Asused herein, journal write commands (e.g., 224) refer to write commandsdirected to a journal area (e.g., 220), whereas regular write commands(e.g., 223) refer to write commands directed to a user LBA space. Thejournal commit commands 225 refer to a sequence of a flush command 226followed by a forced unit access command (to the journal area 220). Aforced unit access command refers to a write command whose correspondingdata is written directly to the memory device, bypassing the writecache. Therefore, a journal commit 225, which is used at the end of aseries of journal writes 224, involves a forced unit access following aflush command such that the data corresponding to the forced unit accessis written directly to the memory device without utilizing a cache ofthe memory sub-system. In contrast to forced unit accesses, the journalwrite commands 224 and regular write commands 223 are written to a cache(e.g., write cache) of the memory sub-system prior to being written tothe memory device (via a flush command). The cache can be implemented invarious locations within a memory subsystem (e.g., 103 shown in FIG. 1).For example, the cache may be located on a memory device such as memorydevice 105, 106 and/or in local memory on the controller 104, amongother locations.

A file system journal (e.g., EXT4 journal) can have identifiable (e.g.,specific) traffic patterns (in terms of IO traffic) associated therewithduring particular system utilization. The robustness and performance ofthe system can be sensitive to the performance of journal area 220. Ifthe storage device can handle the traffic to the journal area 220 withfast performance and reliable data storage, then the user experience maybenefit. Since the locations of one or more journals (e.g., 220) areunknown to a file system, it can be beneficial to identify the journalarea(s) in order to improve system performance.

As an example, consider user updates a database (e.g., when the userinserts a new telephone number, makes a new photo, synchronizes itsaccount with cloud services, among others), which can involve at leasttwo or three write operations in the journal area 220, which may bereferred to as a journal of the journal. In accordance with a number ofembodiments, upon determining the location of a journal area (e.g.,220), the memory sub-system can detect accesses to the journal area 220and can act to speed up the performance of the detected accesses (ascompared to the speed at which the accesses would have been performedhad they not been identified as being directed to the journal area)thereby providing improved database performance and/or user experience.Also, since the write traffic issued to the storage device by aparticular file system is a consistent percentage of the total writetraffic throughout the lifespan of the storage device, by containingthis traffic in specific underling device areas (e.g. in NAND SLCblocks) the overall endurance of the storage device can be enhanced.

A file system provides commands to the memory sub-system utilizing aparticular protocol, such as an embedded multi-media controller (eMMC)protocol or a small computer system interface (SCSI) protocol, forexample. The SCSI protocol can be associated with a universal flashstorage (UFS) device and/or a solid state drive (SSD), for example.

Various examples described herein refer to file system commandsgenerically as read, write, flush, forced unit access, read meta data,write metadata, discard, etc., since the specific file system commandsare protocol dependent, and the file system is likely unaware of theunderlying storage device (e.g., eMMC, UFS, SSD, etc.). Table 1 isprovided as an example mapping of protocol specific commands/flags togeneric file system commands. For example, a read command, as shown inTable 1, can be provided as a READ_10 command using a SCSI protocol. Awrite commands can be provided as a WRITE_10 command using a SCSIprotocol. A forced unit access command can be provided as a WRITE_10with a FUA tag (e.g., flag) using the SCSI protocol. A write commandrelated to user file metadata can be provided as a WRITE_10 commandusing a system data tag (e.g. flag) using the SCSI protocol or a CMD23or a CMD25 with a DATA_TAG tag using the eMMC protocol. As used herein,a read or write command to a metadata area can comprise a command havinga tag such as a DATA_TAG or a system data tag which can be referred toas a data tag.

TABLE 1 eMMC SCSI (e.g. UFS, SSD) Read CMD17/CMD23 + CMD18/ READ_10CMD44 + CMD45 + CMD46 Write CMD24/CMD23 + CMD25/ WRITE_10 (Regular)CMD44 + CMD45 + CMD47 Forced unit CMD23 + CMD25 with WRITE_10 with FUAbit access REL_WRITE bit set set Write CMD23/CMD25 with WRITE_10 usingSystem (Metadata) DATA_TAG bit set Data Tag group number Flush CMD6SYNCHRONIZE_CACHE Discard CMD35/CMD36/CMD38 UNMAP

The EXT4 journal area 220 can have a specific traffic during regularsystem utilization. During regular utilization of the system, thejournal area 220 can be accessed with a number of criteria. For example,a first criteria can include that journal write commands are executed inLBA sequential order. As used herein, LBA sequential order describesthat a journal write at position N and consisting of M LBAs is followedby another journal write at position N+M. For example, an end LBA of afirst write command to the journal area 220 can be adjacent to a startLBA of a second write command to the journal area 220. LBAs (e.g., firstLBA and second LBA) can be adjacent if a first LBA is followed by asecond LBA without a third LBA existing between the first LBA and thesecond LBA.

A second criteria can include that a series of regular write commands tothe journal area 220 (e.g., the journal write commands 224) will endwith a flush command (e.g., flush commands 226-1, 226-2, 226-3, 226-4,and 226-5) followed by a forced unit access command. This specificsequence of a flush command (e.g., 226) followed by a forced unit accesscommand can be referred to as a journal commit (e.g., 225). It is notedthat the journal commit commands 225 represent the combination of aforced unit access command to the journal area 220 and a correspondingrespective flush command 226 immediately preceding the forced unitaccess. As used herein, a flush command refers to a command executed tomove data from cache to a memory device. For example, the journal writecommands 224 can involve writing to cache. The flush command can be usedto commit the data from cache to the memory device. The forced unitaccess command involves storing data corresponding to the journalcommits 225 directly to the memory device without first being written tothe cache (e.g., the write cache is bypassed).

The journal area 220 can be identified (e.g., the particular LBA rangecan be determined) based on the first criteria and/or the secondcriteria. For example, the journal area 220 can be identified bydetermining that the write commands are being executed in sequential LBAorder. The journal area 220 can also be identified based on a flushcommand being followed by a forced unit access command. A forced unitaccess command can be identified by the use of a tag (e.g., REL_WRITEand/or FUA tags).

FIG. 2 shows the sequential and cyclic nature of the journal area 220and the specific sequence of commands used to access the journal area220. In various embodiments, each journal write command 224 (or seriesof journal write commands) is followed by a flush command and a forcedunit access command. As noted above, the specific sequence of a flushcommand 226 followed by a forced unit access command is referred to as arespective journal commit command 225. For example, the journal writecommand 224-1 is sequentially followed by flush command 226-1 and aforced unit access corresponding to the journal commit command 225-1. Asshown in FIG. 2, within the journal area 220, write commands areexecuted in sequential order. For example, the starting LBAcorresponding to journal write 224-2 is adjacent to the end LBAcorresponding to journal commit 225-1. That is, the ending LBA of theforced unit access corresponding to journal commit 225-1 immediatelyprecedes the beginning LBA corresponding to journal write 224-2.

In various embodiments, and as shown in FIG. 2, the journal area 220 canbe implemented as a circular buffer, for example, such that thebeginning and ending LBAs are treated as adjacent LBAs. For instance,the end LBA of the journal commit command 225-3 corresponds to the endLBA of the journal area 220 and the start LBA of the journal writecommand 224-4 corresponds to the start LBA of the journal area 220. Invarious examples, the journal write command 224-4 can be considered asoccurring sequentially to the journal commit 224-3 due to the journalwrite command 224-4 being adjacent to the journal commit command 225-4and the journal commit command 225-4 being adjacent to the journal writecommand 224-1. As described further herein, in accordance with a numberof embodiments of the present disclosure, the cyclic nature of theaccess pattern associated with the journal area 220 can be used toidentify the particular location (e.g., LBA range) of the journal area220 within the LBA space of a memory device.

FIG. 3 illustrates an example of a method for identifying a journal areain accordance with some embodiments of the present disclosure. Themethod can be performed by processing logic that can include hardware(e.g., processing device, circuitry, dedicated logic, programmablelogic, microcode, hardware of a device, integrated circuit, etc.),software (e.g., instructions run or executed on a processing device), ora combination thereof. In some embodiments, the method is performed bythe detection component 109 of FIG. 1. Although shown in a particularsequence or order, unless otherwise specified, the order of theprocesses can be modified. Thus, the illustrated embodiments should beunderstood only as examples, and the illustrated processes can beperformed in a different order, and some processes can be performed inparallel. Additionally, one or more processes can be omitted in variousembodiments. Thus, not all processes are required in every embodiment.Other process flows are possible.

The method includes, at 330, receiving a command (e.g., at a memorysub-system from a host). At 331, the method includes determining whetherthe command is a write command. If the received command is not a writecommand, then it is executed as shown at 339.

If the received command is a write command, at 332, the method includesdetermining whether the received command is contiguous or overlaps witha candidate journal area (e.g., journal, area 220). As used herein, acandidate journal area describes a range of LBAs that may have thepossibility of being a journal area. Access commands to the candidatejournal area can be tracked to determine whether the candidate journalarea is used sufficient to consider the candidate journal area as ajournal area. Overlapping with regards to a candidate journal areadescribes whether the range of LBAs of the received command is withinthe range of LBAs of the candidate journal area. Overlapping can alsodescribe whether the LBAs of the received command are continuous withthe LBAs of the candidate journal area. In FIG. 2, the journal writecommand 224-4 does not overlap with the candidate journal area which caninclude the LBAs of the journal write commands 224-1, 224-2, and 224-3,for example. The journal write commands 224-3 can overlap with thecandidate journal area which includes the LBAs of the journal writecommands 224-1 and 224-2, for example.

If the received command overlaps with the candidate journal area, thenthe method continues to 334. If the received command does not overlapwith the candidate journal area, then the method continues to 333. At333, the received command can be reviewed to determine whether thereceive command is a forced unit access command. The method candetermine whether the received command comprises or is associated with atag. A tag associated with the received command can be reviewed todetermine whether the tag is one of REL_WRITE tag or a FUA tag. If thetag associated with the receive command is one of a REL_WRITE tag or aFUA tag, then the received command can be a forced unit access command.If the received command is a forced unit access command, then the methodcan continue to 334. If the received command is not a forced unit accesscommand, then the method may continue to 339.

Although the method can include determining whether the received methodoverlaps with the candidate journal area and determining whether thereceived command is a forced unit access command, the method can performboth determinations in a different order or only perform one of thedeterminations. For example, the method can determine whether thereceived command is a forced unit access command prior to determiningwhether the received command overlaps with the candidate journal area.The method can, alternatively, only perform one of the determinationsincluding determining whether the received command overlaps with thecandidate journal area or determining whether the received command is aforced unit access command.

At 334, the method can include adding or merging with the list ofcandidate journal areas. A new candidate journal area can be added to alist of candidate journal areas if the received command does not overlapwith a candidate journal area and is a forced unit access command. Thereceived command can be merged with the candidate journal area if thereceived command overlaps with the candidate journal area. A command canbe merged with the candidate journal area if the LBAs of the receivedcommand are merged with (e.g., added to) the LBAs of the candidatejournal area.

The method can then continue to 335. At 335, a determination can be madeas to whether the received command and/or the newly created candidatejournal area is contiguous to an already existing candidate journalarea. A received command or a newly created candidate journal area canbe contiguous if the LBAs of the newly created candidate journal area orthe received command are adjacent to the LBAS of the already existingcandidate journal area. If the received command or the newly createdcandidate journal area is contiguous to the already existing candidatejournal area, then the method continues to 336. If the received commandor the newly created candidate journal area is not contiguous to thealready existing candidate journal area, then the method continues to337.

At 336, a counter can be incremented for the already existing candidatejournal area. The counter can be referred to as a hit counter. Thecounter can represent a use of the already existing candidate journalarea. For instance, the more a candidate journal area is used in acontiguous manner then the more likely the candidate journal area is infact the journal area. The method can continue to 337 after incrementingthe counter for the already existing candidate journal area. At 337, themethod can include determining if the counter for the candidate journalarea is greater than a threshold. If the counter is greater than thethreshold, then the method can mark the received command as a journalwrite command and/or can mark the candidate journal area as a journalarea. Marking the received command as a journal write command and/or thecandidate journal area as a journal area can provide the ability toexpedite execution of the journal write command to limit the stalling ofthe memory device, memory sub-system, and/or computing environment. Themethod can then continue to 339 by executing the received command.

FIG. 4 is a graph illustrating LBAs to which a sequence of commands aredirected and a number of tables (444-1, 444-2, 444-3, 444-4, 444-5, and444-6) corresponding thereto in accordance with some embodiments of thepresent disclosure.

In FIG. 4 the x-axis represents time and the y-axis represents the LBAspace corresponding to the memory device. The graph shows that thejournal write command 442-1 is executed before the journal commitcommand 443-1 and that the journal write command 442-1 and the journalcommit command 443-1 are contiguous. The graph shows that the journalwrite command 442-2 was executed before the journal commit command 443-2and that the journal write command 442-2 and the journal commit command443-2 are contiguous. The graph further shows that the journal writecommand 442-3 was executed before the journal commit command 443-3 andthat the journal write command 442-3 and the journal commit command443-3 are contiguous. The graph shows that the journal write command442-4 was executed before the journal commit command 443-4 and that thejournal write command 442-4 and the journal commit command 443-4 arecontiguous. The graph further shows that the journal write command 442-5was executed before the journal commit command 443-5 and that thejournal write command 442-5 and the journal commit command 443-5 arecontiguous. The example provided in FIG. 4 implements the methodprovided in FIG. 3.

In table 444-1, a first candidate journal area is created responsive tothe journal write command 442-1 being received. The journal writecommand 442-1 can cause data to be written to a start LBA (e.g., 216)and an end LBA (e.g., 217) of the memory device. In this example, thefirst candidate journal area is determined to not overlap with othercandidate journal areas since command 442-1 is the first commandreceived. The counter for the newly created candidate journal area isnot incremented because the newly created candidate journal area and/orthe received command are not contiguous to a different candidate journalarea.

In table 444-2, the journal commit command 443-1 overlaps with the firstcandidate journal area and is a forced unit access command resulting ina merger of the journal commit command 443-1 with the first candidatejournal area. The journal commit command 443-1 can cause data to bewritten to a start LBA (e.g., 217) and an end LBA (e.g., 232). Giventhat the journal commit command 443-1 is contiguous with the firstcandidate journal area, the counter associated with the first candidatejournal area is incremented (e.g., 1). The contiguousness of a journalcommit command and/or a journal write command with a candidate journalarea can be referred to as a “hit”. The counter can be incremented ifthere is a hit (e.g., if a journal commit command and/or a journal writecommand is contiguous with a candidate journal area). The journal commitcommand 443-1 may not be labeled as a journal write command given thatthe counter associated with the first candidate journal area is notgreater than a threshold. A threshold can be, for example, more than 100hits. Although the threshold can be more or less than 100 hits. Thejournal commit command 443-1 can be executed.

In table 444-3, the journal write command 442-2 overlaps with the firstcandidate journal area resulting in a merger of the journal writecommand 442-2 with the first candidate journal area. Given that thejournal write command 442-2 is contiguous with the first candidatejournal area, the counter associated with the first candidate journalarea is incremented (e.g., 2). The journal write command 442-2 may notbe labeled as a journal write command given that the counter associatedwith the first candidate journal area is not greater than a threshold.The journal write command 442-2 can be executed. In table 444-3, thejournal commit command 443-2 also overlaps with the first candidatejournal area and is a forced unit access command resulting in a mergerof the journal commit command 443-2 with the first candidate journalarea. Given that the journal commit command 443-2 is contiguous with thefirst candidate journal area, the counter associated with the firstcandidate journal area is incremented (e.g., 3). The journal commitcommand 443-2 may not be labeled as a journal write command given thatthe counter associated with the first candidate journal area is notgreater than a threshold. The journal commit command 443-2 can beexecuted.

In table 444-4, the journal write command 442-3 overlaps with the firstcandidate journal area resulting in a merger of the journal writecommand 442-3 with the first candidate journal area. Given that thejournal write command 442-3 is contiguous with the first candidatejournal area, the counter associated with the first candidate journalarea is incremented (e.g., 100+). The journal write command 442-3 may belabeled as a journal write command given that the counter associatedwith the first candidate journal area is greater than a threshold. Thejournal write command 442-3 can be executed differently than theexecution of the journal write commands 442-1 and 442-2 based on theidentification of the command 442-3 as a journal write command. In table444-4, the journal commit command 443-3 also overlaps with the firstcandidate journal area and is a forced unit access command resulting ina merger of the journal commit command 443-3 with the first candidatejournal area. Given that the journal commit command 443-3 is contiguouswith the first candidate journal area, the counter associated with thefirst candidate journal area is incremented (e.g., 100+). The command443-3 may be labeled as a journal write command given that the counterassociated with the first candidate journal area is greater than athreshold. The journal commit command 443-3 can be executed.

In table 444-5, the journal write command 442-4 does not overlap withthe first candidate journal area resulting in a new candidate journalarea being created. The new candidate journal area can be referred to asa second candidate journal area. Given that the journal write command442-4 or the second candidate journal area is not contiguous with thefirst candidate journal area, the counter associated with the firstcandidate journal area is not incremented. The journal write command442-4 may not be labeled as a journal write command given that thecounter associated with the second candidate journal area is not greaterthan a threshold.

Although not shown, the journal commit command 443-4 overlaps with thesecond candidate journal area but does not overlap with the firstcandidate journal area, and is a forced unit access command resulting ina merger of the journal commit command 443-4 with the second candidatejournal area. Given that the journal commit command 443-4 is contiguouswith the second candidate journal area, the counter associated with thesecond candidate journal area is incremented (e.g., 1). The journalcommit command 443-4 may not be labeled as a journal write command giventhat the counter associated with the first candidate journal area is notgreater than a threshold. The journal commit command 443-4 can beexecuted.

In table 444-6, the journal write command 442-5 overlaps with the secondcandidate journal area resulting in a merger of the journal writecommand 442-5 with the second candidate journal area. Given that thejournal write command 442-5 or the second candidate journal area is notcontiguous with the first candidate journal area, the counter associatedwith the first candidate journal area is not incremented although thecounter associated with the second candidate journal area isincremented. The journal write command 442-5 may not be labeled as ajournal write command given that the counter associated with the secondcandidate journal area is not greater than a threshold.

The journal commit command 443-5 overlaps with the second candidatejournal area and the first candidate journal area, and is a forced unitaccess command resulting in a merger of the journal commit command 443-4with the first candidate journal area and the second candidate journalarea. The first candidate journal area and the second candidate journalarea can also be merged given that they are contiguous. Given that thejournal commit command 443-5 is contiguous with the second candidatejournal area and the first candidate journal area, the counterassociated with the first candidate journal area is incremented (e.g.,100+). The journal commit command 443-5 may be labeled as a journalwrite command given that the counter associated with the first candidatejournal area is greater than a threshold. The journal commit command443-5 can be executed. Merging two different candidate journal areas canresult in the deletion of one of the candidate journal areas and thecontinuity of the other candidate journal area.

FIG. 5 illustrates an example of a metadata area 551 in accordance withsome embodiments of the present disclosure. As previously described, theexamples of FIG. 5 and FIG. 6 are provided in the context of the F2FS.

The layout of the F2FS can include a superblock area, a checkpoint area,a segment info table (SIT) area, a node address table (NAT) area, asegment summary (SS) area, and a main area. The superblock (SB) area isaccessed during platform boot in read mode and at format time in writemode. The checkpoint (CP) area is accessed using a forced unit accesscommand. The SIT, NAT, and/or SS areas are accessed using metadata readand write commands. Commands used to read or write to the metadata area551 can be tagged (e.g., flagged) with the DATA_TAG tag. The main areais accessed with regular read and write commands to access user datafrom a user area 552.

FIG. 5 shows a graph comprising a range of LBAs 520. The range of LBAs520 includes a start LBA and an end LBA for the metadata area 551 andthe user area 552.

FIG. 6 illustrates an example of a metadata area in accordance with someembodiments of the present disclosure. FIG. 6 includes a graphcomprising an x-axis representing time 621 and a y-axis representingLBAs 620. The graph shows write commands 623, metadata write commands661-1, 661-2, 661-3, and 661-4, and checkpoint commands 662-1 and 662-2.The metadata write commands 661-1, 661-2, 661-3, and 661-4 can bereferred to as metadata write commands 661. The checkpoint commands662-1 and 662-2 can be referred to as checkpoint commands 662. Thecheckpoint commands 662 can also be referred to as forced unit accesscommands 662. The existence of a checkpoint can be used to identify thatthe file system is an F2FS. Furthermore, forced unit access commands toa same range of LBAs can signify use of the F2FS.

The F2FS traffic can be divided in a number of phases. A first phase caninclude writing and reading data from a user area (e.g., the user area552 in FIG. 5) using access commands 623 (e.g., write commands and/orread commands, for example). During the first phase a plurality ofcommands are directed to the user area. The plurality of commandsincludes the read command, the write command, the flush command, and thediscard command, among other possible commands. Some of the commands inthe first phase can also be directed to the metadata area including theSIT area, the NAT area, and/or the SS area (e.g., SSA).

A second phase can include flushing metadata. During the second phasewrite commands are directed to the metadata area including the SIT area,the NAT area, and/or the SSA. The write commands to the metadata areacan be identified using the DATA_TAG tag, for example. A third phase caninclude flushing and checkpoints. The end of the third phase is markedby a flush command followed by a write to the checkpoint area. The writeto the checkpoint area can be a forced unit access command. Thecheckpoint area can be identified by identifying commands that areforced unit access commands 662.

The second phase and the third phase can be identified at a protocollevel. For example, in an eMMC protocol the start of the second phasecan be identified by monitoring a DATA_TAG tag in write operations. Thethird phase can be detected by monitoring for the REL_WRITE tag. Forexample, a REL_WRITE tag can be identified in a write command. Theidentification of the REL_WRITE tag can be used to identify the thirdphase. The REL_WRITE tag can also be used to identify that a command isa forced unit access command. The detection circuitry (e.g., detectioncircuitry in FIG. 1) can take actions to improve latency of theoperations when the second and third phase are detected. For example,identifying the second phase and the third phase can allow for adetermination of the file system being used. Identifying the secondphase and the third phase can provide for the determination of themetadata area and an identification of an IO pattern.

In FIG. 6 the metadata write commands 666-1 and 666-2 can be identifiedresponsive to the metadata write commands 666-1 and 666-2 utilizing aDATA_TAG tag. The flush commands can be used to identify the end of thesecond phase and the beginning of the third phase. The use of aREL_WRITE tag with a command can signal the checkpoint area. Thecheckpoint area can occur in the same LBAs such that repeated commandsto a same number of LBAs can also signal the checkpoint area/the thirdphase. The LBA's of the checkpoint area can be determined based on theLBA's of the forced unit access commands. For example, the start LBA andend LBA of the checkpoint can be determined as the start LBA and the endLBA of the forced unit access commands 662-1 and 662-2. The start LBAand end LBA of the forced unit access commands 662-1 and 662-2 can beused (e.g., assigned) as the start LBA and end LBA of the checkpointarea. The forced unit access commands 662-1 and 662-2 can be monitoredto ensure that the forced unit access commands 662-1 and 662-2 have thesame start LBA and end LBA.

The metadata write commands 661-3 and 661-4 can be observed. The LBAscorresponding to the metadata write commands 661-3 and 661-4 can bedifferent than the LBAs corresponding to the metadata write commands661-1 and 661-2. The LBAs of the metadata area can be updated if themetadata write commands 661-3 and 661-4 utilize commands that have adifferent LBA range than the metadata write commands 661-1 and 661-2.

FIG. 7 is a flow diagram of an example method 780 corresponding todetection circuitry in accordance with some embodiments of the presentdisclosure. The method 780 can be performed by processing logic that caninclude hardware (e.g., processing device, circuitry, dedicated logic,programmable logic, microcode, hardware of a device, integrated circuit,etc.), software (e.g., instructions run or executed on a processingdevice), or a combination thereof. In some embodiments, the method 780is performed by the detection component 109 of FIG. 1. Although shown ina particular sequence or order, unless otherwise specified, the order ofthe processes can be modified. Thus, the illustrated embodiments shouldbe understood only as examples, and the illustrated processes can beperformed in a different order, and some processes can be performed inparallel. Additionally, one or more processes can be omitted in variousembodiments. Thus, not all processes are required in every embodiment.Other process flows are possible.

At 781, a command can be received at a memory sub-system. At 782, adetermination can be made as to whether the received command is a writecommand. For example, it can be determined whether the command is aregular write command and/or a forced unit access command. At 783,responsive to determining that the received command is a write command,a determination can be made as to whether the write command is a forcedunit access command. At 784, responsive to determining that the writecommand is a forced unit access command, a start LBA and an end LBA of acandidate journal area of a memory device of the memory sub-system canbe determined. At 785, the candidate journal area can be marked as ajournal area of the memory device responsive to the candidate journalarea being accessed a threshold number of times. At 786, an action canbe taken responsive to a subsequent access to the journal area.

The method 780 can further comprise receiving a different command at thememory sub-system. The method 780 can also include, responsive todetermining that the received different command is a different writecommand, determining whether a start LBA and an end LBA for thedifferent write command overlaps with the start LBA and the end LBA ofthe candidate journal area. Responsive to determining, via controlcircuitry of the memory sub-system, that the start LBA and the end LBAfor the different write command overlaps with the start LBA and the endLBA of the candidate journal area, the start LBA and the end LBA of thecandidate journal area can be updated to include the start LBA and theend LBA of the different write command. Updating the start LBA and theend LBA of the candidate journal area can include setting the start LBAand/or the end LBA of the different write command as the start LBAand/or the end LBA of the candidate journal area such that thedifference between the start LBA and the end LBA of the candidatejournal area is greater than prior to the updating. Responsive todetermining that the start LBA and the end LBA for the different writecommand does not overlap with the start LBA and the end LBA of thecandidate journal area, a determination can be made as to whether thedifferent write command is a different forced unit access command.

Responsive to determining that the different write command is adifferent forced unit access command, a new candidate journal area canbe added where the new candidate journal area has a start LBA and an endLBA corresponding to the start LBA and the end LBA of the differentforced unit access command. Responsive to determining that the differentwrite command is not a forced unit access command, the command can beexecuted without marking the candidate journal area as the journal area.

Responsive to adding the new candidate journal area or updating thestart LBA and the end LBA of the candidate journal area, a determinationcan be made as to whether the start LBA or the end LBA of the differentwrite command is continuous to the start LBA or the end LBA of thecandidate journal area or the new candidate journal area. Responsive todetermining that the start LBA or the end LBA of the different writecommand is continuous to the start LBA or the end LBA of the candidatejournal area of the new candidate journal area, an area hit counter forthe candidate journal area or the new candidate journal area can beincremented.

Responsive to determining that the area hit counter of the candidatejournal area is greater than the threshold, the candidate journal areacan be marked as the journal area. Responsive to determining that thearea hit counter of the new candidate journal area is greater than thethreshold, the new candidate journal area can be marked as the journalarea. The new command can be executed responsive to marking thecandidate journal area as the journal area and/or marking the newcandidate journal area as the journal area.

Responsive to determining that the area hit counter of the candidatejournal area is not greater than the threshold, the candidate journalarea may not be marked as the journal are and the new command can beexecuted. Responsive to determining that the area hit counter of the newcandidate journal area is not greater than the threshold, the newcandidate journal area may not be marked as the journal area and the newcommand can be executed.

In various instances, a system can comprise a controller coupled to amemory device. The controller can be configured to monitor a pluralityof received commands to identify a forced unit access command, identifya metadata area of the memory device based on the forced unit accesscommand, and perform an action responsive to identifying a subsequentforced unit access command to the metadata area.

The controller can further identify a plurality of forced unit accesscommands including the forced unit access command and identify themetadata area of the memory device based on the plurality of forced unitaccess commands. The controller can also determine a start LBA and anend LBA for each of the plurality of forced unit access command. Thecontroller can further determine a start LBA and an end LBA for themetadata area based at least on the start LBA and end LBA for each ofthe plurality of forced unit access commands.

In various examples, a system can comprise a controller coupled to amemory device and configured to identify a file system utilizing aplurality of access commands to the memory device and, responsive toidentifying the file system, determine a start LBA and an end LBA of ametadata area of the memory device based on the plurality of accesscommands and the file system. The controller can further determine awrite pattern of the plurality of access commands utilizing the startLBA, the end LBA, and the plurality of access commands and can performan action based on the write pattern.

An F2FS can be identified utilizing the plurality of access commands tothe memory device. A determination can be made as to whether the writepattern of the plurality of access commands is further configured toidentify a checkpoint area of the metadata area. The checkpoint area canbe identified utilizing a plurality of forced unit access commands fromthe plurality of access commands to the memory device. A start LBA andan end LBA for the plurality of forced unit access commands can bedetermined and the start LBA and the end LBA of the plurality of forcedunit access commands can be assigned as a start LBA and an end LBA ofthe checkpoint area. Each of the plurality of forced unit accesscommands can be determined as having a same start LBA and a same endLBA. The start LBA of the check point can be assigned as the start LBAof the metadata area.

FIG. 8 illustrates an example machine of a computer system 890 withinwhich a set of instructions, for causing the machine to perform one ormore of the methodologies discussed herein, can be executed. In someembodiments, the computer system 890 can be analogous to the memorysub-system controller 104 of FIG. 1. In alternative embodiments, themachine can be connected (e.g., networked) to other machines in a LAN,an intranet, an extranet, and/or the Internet. The machine can operatein the capacity of a server or a client machine in client-server networkenvironment, as a peer machine in a peer-to-peer (or distributed)network environment, or as a server or a client machine in a cloudcomputing infrastructure or environment.

The machine can be a personal computer (PC), a tablet PC, a set-top box(STB), a Personal Digital Assistant (PDA), a cellular telephone, a webappliance, a server, a network router, a switch or bridge, or anothermachine capable of executing a set of instructions (sequential orotherwise) that specify actions to be taken by that machine. Further,while a single machine is illustrated, the term “machine” shall also betaken to include a collection of machines that individually or jointlyexecute a set (or multiple sets) of instructions to perform one or moreof the methodologies discussed herein.

The example computer system 890 includes a processing device 892, a mainmemory 894 (e.g., read-only memory (ROM), flash memory, dynamic randomaccess memory (DRAM) such as synchronous DRAM (SDRAM) or Rambus DRAM(RDRAM), etc.), a static memory 898 (e.g., flash memory, static randomaccess memory (SRAM), etc.), and a data storage system 899, whichcommunicate with each other via a bus 897. The data storage system 899can be a memory sub-system such as memory sub-system 103 described inFIG. 1 (e.g., UFS, eMMC, etc.).

The processing device 892, which can be analogous to the processor 107in FIG. 1, represents one or more general-purpose processing devicessuch as a microprocessor, a central processing unit, or the like. Moreparticularly, the processing device can be a complex instruction setcomputing (CISC) microprocessor, reduced instruction set computing(RISC) microprocessor, very long instruction word (VLIW) microprocessor,or a processor implementing other instruction sets, or processorsimplementing a combination of instruction sets. The processing device892 can also be one or more special-purpose processing devices such asan application specific integrated circuit (ASIC), a field programmablegate array (FPGA), a digital signal processor (DSP), network processor,or the like. The processing device 892 is configured to executeinstructions 893 for performing the operations and steps discussedherein. The computer system 890 can further include a network interfacedevice 895 to communicate over the network 896.

The data storage system 899 can include a machine-readable storagemedium 891 (also known as a computer-readable medium) on which is storedone or more sets of instructions 893 or software embodying one or moreof the methodologies or functions described herein. The instructions 893can also reside, completely or at least partially, within the mainmemory 894 and/or within the processing device 892 during executionthereof by the computer system 890, the main memory 894 and theprocessing device 892 also constituting machine-readable storage media.The machine-readable storage medium 891, data storage system 899, and/ormain memory 894 can correspond to the memory sub-system 103 of FIG. 1.

In one embodiment, the instructions 893 include instructions toimplement functionality corresponding to the detection component 109 ofFIG. 1. The instructions can include a command instruction 889associated with recognizing a file system, detecting a metadata area,and detecting an IO pattern for the metadata area (e.g., detectioncomponent 109 in FIG. 1). While the machine-readable storage medium 891is shown in an example embodiment to be a single medium, the term“machine-readable storage medium” should be taken to include a singlemedium or multiple media that store the one or more sets ofinstructions. The term “machine-readable storage medium” shall also betaken to include a medium that is capable of storing or encoding a setof instructions for execution by the machine and that cause the machineto perform one or more of the methodologies of the present disclosure.The term “machine-readable storage medium” shall accordingly be taken toinclude, but not be limited to, solid-state memories, optical media, andmagnetic media.

Some portions of the preceding detailed descriptions have been presentedin terms of algorithms and symbolic representations of operations ondata bits within a computer memory. These algorithmic descriptions andrepresentations are the ways used by those skilled in the dataprocessing arts to most effectively convey the substance of their workto others skilled in the art. An algorithm is here, and generally,conceived to be a self-consistent sequence of operations leading to adesired result. The operations are those requiring physicalmanipulations of physical quantities. Usually, though not necessarily,these quantities take the form of electrical or magnetic signals capableof being stored, combined, compared, and otherwise manipulated. It hasproven convenient at times, principally for reasons of common usage, torefer to these signals as bits, values, elements, symbols, characters,terms, numbers, or the like.

It should be borne in mind, however, that all of these and similar termsare to be associated with the appropriate physical quantities and aremerely convenient labels applied to these quantities. The presentdisclosure can refer to the action and processes of a computer system,or similar electronic computing device, that manipulates and transformsdata represented as physical (electronic) quantities within the computersystem's registers and memories into other data similarly represented asphysical quantities within the computer system memories or registers orother such information storage systems.

The present disclosure also relates to an apparatus for performing theoperations herein. This apparatus can be specially constructed for theintended purposes, or it can include a general purpose computerselectively activated or reconfigured by a computer program stored inthe computer. Such a computer program can be stored in a computerreadable storage medium, such as, but not limited to, types of diskincluding floppy disks, optical disks, CD-ROMs, and magnetic-opticaldisks, read-only memories (ROMs), random access memories (RAMs), EPROMs,EEPROMs, magnetic or optical cards, or type of media suitable forstoring electronic instructions, each coupled to a computer system bus.

The algorithms and displays presented herein are not inherently relatedto a particular computer or other apparatus. Various general purposesystems can be used with programs in accordance with the teachingsherein, or it can prove convenient to construct a more specializedapparatus to perform the method. The structure for a variety of thesesystems will appear as set forth in the description below. In addition,the present disclosure is not described with reference to a particularprogramming language. It will be appreciated that a variety ofprogramming languages can be used to implement the teachings of thedisclosure as described herein.

The present disclosure can be provided as a computer program product, orsoftware, that can include a machine-readable medium having storedthereon instructions, which can be used to program a computer system (orother electronic devices) to perform a process according to the presentdisclosure. A machine-readable medium includes a mechanism for storinginformation in a form readable by a machine (e.g., a computer). In someembodiments, a machine-readable (e.g., computer-readable) mediumincludes a machine (e.g., a computer) readable storage medium such as aread only memory (“ROM”), random access memory (“RAM”), magnetic diskstorage media, optical storage media, flash memory devices, etc.

In the foregoing specification, embodiments of the disclosure have beendescribed with reference to specific example embodiments thereof. Itwill be evident that various modifications can be made thereto withoutdeparting from the broader spirit and scope of embodiments of thedisclosure as set forth in the following claims. The specification anddrawings are, accordingly, to be regarded in an illustrative senserather than a restrictive sense.

What is claimed is:
 1. A system comprising: a memory device; acontroller coupled to the memory device and configured to: monitor aplurality of received commands to identify a forced unit access command;identify a metadata area of the memory device based on the forced unitaccess command; responsive to determining that a start LBA and an endLBA for a different write command overlaps with a start LBA and an endLBA of the metadata area, update the start LBA and the end LBA of themetadata area to include the start LBA and the end LBA of the differentwrite command; responsive to determining that the start LBA and the endLBA for the different write command does not overlap with the start LBAand the end LBA of the metadata area, determining whether the differentwrite command is a different forced unit access command; and perform anaction responsive to identifying a subsequent forced unit access commandto the metadata area.
 2. The system of claim 1, wherein the controlleris further configured to: identify a plurality of forced unit accesscommands including the forced unit access command; and identify themetadata area of the memory device based on the plurality of forced unitaccess commands.
 3. The system of claim 2, wherein the controller isfurther configured to determine a start logical block address (LBA) andan end LBA for each of the plurality of forced unit access command. 4.The system of claim 3, wherein the controller configured to identify themetadata area is further configured to determine the start LBA and theend LBA for the metadata area based at least on the start LBA and endLBA for each of the plurality of forced unit access commands.
 5. Amethod comprising: receiving a command at a memory sub-system;determining whether the received command is a write command; responsiveto determining that the received command is a write command, determiningwhether the write command is a forced unit access command; responsive todetermining that the write command is a forced unit access command,determining a start LBA and an end LBA of a candidate journal area of amemory device of the memory sub-system; receiving a different command atthe memory sub-system; responsive to determining that the receiveddifferent command is a different write command, determining whether astart LBA and an end LBA for the different write command overlaps withthe start LBA and the end LBA of the candidate journal area; responsiveto determining, via control circuitry of the memory sub-system, that thestart LBA and the end LBA for the different write command overlaps withthe start LBA and the end LBA of the candidate journal area, updatingthe start LBA and the end LBA of the candidate journal area to includethe start LBA and the end LBA of the different write command; andresponsive to determining that the start LBA and the end LBA for thedifferent write command does not overlap with the start LBA and the endLBA of the candidate journal area, determining whether the differentwrite command is a different forced unit access command; marking thecandidate journal area as a journal area of the memory device responsiveto the candidate journal area being accessed a threshold number oftimes; and taking an action responsive to a subsequent access to thejournal area.
 6. The method of claim 5, further comprising: responsiveto determining that the different write command is a different forcedunit access command, adding a new candidate journal area having a startLBA and an end LBA of the different forced unit access command; andresponsive to determining that the different write command is not aforced unit access command, executing the command without marking thecandidate journal area as the journal area.
 7. The method of claim 6,further comprising: responsive to adding the new candidate journal areaor updating the start LBA and the end LBA of the candidate journal area,determining whether the start LBA or the end LBA of the different writecommand is continuous to the start LBA or the end LBA of the candidatejournal area or the new candidate journal area; and responsive todetermining that the start LBA or the end LBA of the different writecommand is continuous to the start LBA or the end LBA of the candidatejournal area of the new candidate journal area, incrementing an area hitcounter for the candidate journal area or the new candidate journalarea.
 8. The method of claim 7, further comprising: responsive todetermining that the area hit counter of the candidate journal area isgreater than the threshold, marking the candidate journal area as thejournal area; responsive to determining that the area hit counter of thenew candidate journal area is greater than the threshold, marking thenew candidate journal area as the journal area; and executing the newcommand.
 9. The method of claim 8, further comprising: responsive todetermining that the area hit counter of the candidate journal area isnot greater than the threshold: refraining from marking the candidatejournal area as the journal area; and executing the new command.
 10. Themethod of claim 8, further comprising: responsive to determining thatthe area hit counter of the new candidate journal area is not greaterthan the threshold: refraining from marking the new candidate journalarea as the journal area; and executing the new command.
 11. The methodof claim 5, wherein the write command is one of a journal write commandand a journal commit command.
 12. A system comprising: a memory device;a controller coupled to the memory device and configured to: identify afile system utilizing a plurality of access commands to the memorydevice and responsive to determining that at least one of the pluralityof access commands is a forced unit access command; responsive toidentifying the file system, determine a start logical block address(LBA) and an end LBA of a metadata area of the memory device based onthe plurality of access commands and the file system; responsive todetermining that a start LBA and an end LBA for a different accesscommand overlaps with the start LBA and the end LBA of the metadataarea, update the start LBA and the end LBA of the metadata area toinclude the start LBA and the end LBA of the different access command;responsive to determining that the start LBA and the end LBA for thedifferent access command does not overlap with the start LBA and the endLBA of the metadata area, determining whether the different accesscommand is a different forced unit access command; determine a writepattern of the plurality of access commands utilizing the start LBA, theend LBA, and the plurality of access commands; and perform an actionbased on the write pattern.
 13. The system of claim 12, wherein thecontroller configured to identify the file system is further configuredto identify a Flash Friendly Filesystem (F2FS) utilizing the pluralityof access commands to the memory device.
 14. The system of claim 12,wherein the controller configured to determine the write pattern of theplurality of access commands is further configured to identify acheckpoint area of the metadata area.
 15. The system of claim 14,wherein the controller configured to identify the checkpoint area isfurther configured to identify the checkpoint area utilizing a pluralityof forced unit access commands from the plurality of access commands tothe memory device.
 16. The system of claim 15, where the controller isfurther configured to: determine a start LBA and an end LBA for theplurality of forced unit access commands; and assign the start LBA andthe end LBA of the plurality of forced unit access commands as a startLBA and an end LBA of the checkpoint area.
 17. The system of claim 16,wherein the controller configured to determine the start LBA and the endLBA for the plurality of forced unit access commands is furtherconfigured to determine that each of the plurality of forced unit accesscommands has a same start LBA and a same end LBA.
 18. The system ofclaim 16, wherein the controller is further configured to assign thestart LBA of the check point as the start LBA of the metadata area.